

highly recommended
Definitely a keeper!

Great Inspiration to Other SurvivorsI can't wait to see the movie and read the next book!
Excellent! From Victim to Investigator ....

reviewused booksale.He was surprised by it and liked it.
This would be a great movie ;but,would not be very flattering
to the US military and the politics behind Reaganism of the
1980's,1990's,and (retro 1990's) present political hysteria and
military drama . Great read for Tom Clancy readers who find
Dan Quayle to be a brainiac compared to G.Dubbuh Bush--du jour of the oval office. Und you vill like it!
Very euro -esiponage of the 1980's....


CLEAN SLATE

Out of Print! That's awful!

THat goods

Excellent parenting insights for dogs and childrenThe comparisons are interesting both for application to man's best friend and children. The key concept developed is what is leadership and what are the responsibilities of the pack leader (Alpha--male/female).
The text is very application-oriented and provides many examples, both positive and negative, of behaviors and responses.
Finally, the leadership skills discussed in the text may very well have applications beyond just dogs and children, perhaps business management as well.
Fun reading with many applications and yet doesn't fail to maintain the focus on developing a better relationship with your canine friend.


An excellant view of drugs, crime, prison, and redemption

Teaches the Concept of Teaching ConceptsThe layout of the book is the perfect example of concept instructional design. Each step in the process has its own chapter, which makes the book well organized and easy to follow. Each term is thoroughly illustrated and defined. It is supplemented by examples, which compliment the design of the book, and questions, which keep the reader involved. The book is divided into ten chapters providing in-depth outlines of the 10 steps involved in the concept instruction design process. Thankfully, the authors did not forget the all-important formative and summative evaluation components of instructional design. The appendix contains sample concept lessons designed by three of Dr. Merrill's former students. There are also several concept lessons that have been completed and included for reference.
The bottom line: When seeking an instructional design guide for concepts, I would highly recommend this text to instructional designers, instructors, students, and anyone in the instructional design field.


PracticalThe only quirk I found in the book was the diatribe against the benefit of CMM or knowledge of other models. I understand their point, which is that these models don't really add value to the hands on aspect of testing or developing software. However, from personal experience, I have seen a greater tendency in developers to consider many of the points they make if their background includes an appreciation for the types of things that should happen in a mature organization.
Invaluable for all Test AutomatorsToo many times have automated test tools become shelfware, or the cost of maintaining the scripts prohibitvely expensive. The authors of this book offer a simple and easy to use data-driven framework that can minimise scripts and human effort. They place their framework within the Rational Unified Process (RUP).
The book offers actual and detailed advice that goes all the way down to code and script templates. Based mostly on Rational tools, the book gives lip service to Winrunner and anything said can be translated to any automated tool.
Their open-source framework is the Control Synchronized Data Driven Testing(CSDDT). Data to be input, keywords to navigate through the application and actions to be performed are held in the spreadsheet. There are four main scripts: A Main script that reads and processes the records; a window selection script, a tab selection script, an action script and error handling script. Data input is held in an array and there is a comment field that documents the test record. Your application code is held in a switch statement, and it is highly conceivable that your project can have single figure script numbers. There is also a script that converts the spreadsheet data in a .csv file that is read by the Main script. There is detailed
information given on how to implement the CSDDT. It is a framework I use and am pleased with.
There are two interesting chapters on Unit and Integration testing. Like eXtreme Programmers they believe in automating unit tests that pass at 100% before submitting for build. They correctly argue that unit tests should be constructed before development code is written and they also point to the xUnit group of tools.
They make insightful points about the necessity of integration testing: Could you not help but identify with the following statements: "... We have seen two chronic problems: First, the build fequently does not install on system test machines. Second, the fact that unit and integration testing has not been done previously forces the system test team to do tests that development should have already executed." Again they also argue for automated integration testing else "it will not get done."
I feel however that Mosley and Posey's ideas need to be infused with agile values and practices. For example do we really need improved software requirements documentation, verbose Test Plans and meticulous test design when requirements change so much? Do we really need all these Rational tools and the time it takes to use and update them? Can we not make automated functional tests an integral part of requirements? What about Pair Test Programming? How are we going to increase oral communication? Is devolopment and test a false dichotomy? These kind of issues also need to be addressed as we begin to construct software in a radically different way.
Practically speaking: Fundamentals, experience and how to'sWhile the book is well written and easy to read for someone who's familiar with software testing and who may have some experience with test automation, it assumes that the reader does have experience in the field.
The authors begin by reviewing important fundamental practices of software testing that are critical to effectively sustaining both manual and automated testing efforts. They provide recommendations on how to approach test automation for each phase of the software development lifecycle beginning with requirements through the final stages of testing. The authors present very specific recommended techniques and tools and offer many examples using a data driven framework with emphasis on Control Synchronized Data Driven Testing (CSDDT). Most often the tools mentioned and examples provided are those offered by Rational, Inc. as well as the use of Microsoft Excel. Frequently, automated tools from other vendors are referenced when they are applicable to the technique being discussed. They provide references to books and to several web links that offer sources of information on similar frameworks using other tools. The authors include useful information in the appendices such as a captured discussion on the subject of the data driven approach by leading practitioners, automated testing definitions, an example test automation project plan, and a test automation project work plan template.
Some of the key points in the book include the importance of identifying and documenting application and testing requirements as well as documenting test cases and conditions. They emphasize the importance of planning for test automation and implementing it similar to any other software development effort. This includes the separation of roles between test designer and test implementer. They urge that test automation be performed at most phases of software development including unit testing, but that it primarily be used for regression testing. The key success factor for test automation is the maintainability of test scripts. The authors point out that this is extremely difficult using a capture/playback method of implementation and that a data driven approach using modular scripts has shown to be much more successful in the long run. The authors do a good job of describing these key points and then making specific recommendations with examples on how to implement them.
As a practitioner of test automation, and reviewer of this book, I very much agree with these key recommendations and support the authors' intent to educate people implementing test automation as these key points can be the difference between failure and success.
Anistasia Kirk, Anna, struggles to save an albatross, plummeting herself into a adventure with David Morgan, who sees past the cool business woman façade she attempts to maintain, to the erotic, sensually passionate woman. When he reawakens her passion long held in check, she leaves him, without even a name, to return to her normal life.
The following night she and her fiancé Hugh hold their engagement party, but Anna finds herself shocked when Hugh introduces the mysterious stranger from the night before as his best friend.
Anna finds it more and more difficult to repress her emotions in the ensuing months as she spends more time in David's company. The stubbornness that she turned into tenacity in the business world, the passion she squelched to remain professional, and the sensuality repressed beneath business suits and sensible heels threatens both her security in her self-created world, and her relationship with her father. As David continues to coax the smoldering passions within Anna to a flame, she finds herself torn between like her mother who died mysteriously years before, and the sensible woman she had vowed to become.
EYES OF A STRANGER is a marvelously sensual romance with a heady rush to the senses and is written with flare and panache. When David promises Anna "I am the only man with whom you can allow your nature free reign and I am the only man who understands and accepts you as you are," even the most jaded of readers can't help but be swept away.